docs(changelog): record what 0.4.0 actually ships - #30
Merged
Conversation
Twenty-three commits landed since v0.3.0 and the 0.4.0 section described four of them. Most of the rest are CI and repository hygiene that a changelog should not carry, but three were real and missing: the move to Node 24, the step from `@kkdev92/vscode-ext-kit` ^3.0.0-alpha.1 to the released ^3.0.0, and the eslint and typescript-eslint bumps. Every version here was read back out of package-lock.json rather than copied from the pull request that bumped it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Found while preparing the release notes for
v0.4.0: 23 commits landed sincev0.3.0and the changelog section described four of them.Most of the remainder is CI and repository hygiene a changelog should not carry — pinned actions, Scorecard, badge and docs work. Three were real and missing:
engines.node>=22.12.0→>=24.0.0,@types/node22 → 24). Contributor-facing, not user-facing — VS Code supplies the Node that runs the extension.@kkdev92/vscode-ext-kit^3.0.0-alpha.1→^3.0.0. 0.3.0 shipped against an alpha.eslint10.8.0 → 10.9.1,typescript-eslint8.65.0 → 8.68.0, andlintnow fails on warnings.Every version was read back out of
package-lock.json, not copied from the PR that bumped it.Documentation only — no code, no version change. Blocks tagging
v0.4.0, since the tag is immutable and the release notes come from here.